V317 - Death Escape / No Player 1 Manual Pause / Host Campaign Continuation
Base: V316, keeping the V313-V316 join, cutscene, multiplayer, account,
character ownership, and native Import/Export behavior.

WHAT CHANGES
1. When WORLD_DEATH appears, Escape can open the regular Options panel. The
   death menu no longer ignores Escape. Death is NOT reversed or bypassed.
2. If the game still shows the world during a cutscene after ALL visible party
   members' HP reach 0, the global Escape listener recognizes this dead-party
   state before applying the normal story cutscene Escape prohibition.
   Ordinary cutscenes still cannot be skipped by Escape.
3. Player-controlled pauses remain blocked: the clock is not clickable and
   both the UI pause shortcut and EEex pressed-key listener handle Space.
   Both ASCII 32 and physical scan key 57 are covered. Multiplayer host/player1
   gets no special manual pause right. Dialogues, scripts and transient native
   join synchronization pauses are not forcibly unpaused or modified.
4. The authenticated live protagonist can use SAVE GAME in Options while alive,
   outside cutscenes, and while hosting (or during their single-player session).
   No save occurs automatically. A dead player cannot save their position.
5. Each native save is named with an unambiguous account/campaign prefix, e.g.
   DRK09_drakhysys_SoA_Campaign Progress. The account/campaign string makes
   Save/Overwrite/Delete and Resume UI refuse other accounts' native save slots.
6. When creating a host campaign, choose RESUME CAMPAIGN instead of NEW GAME.
   Only the authenticated account/campaign's saved slots can load from this
   entrypoint. Clients still join the protagonist's actual running world.
7. The account router records a per-campaign reference to the most recent
   completed native multiplayer save in:
     Documents/Baldur's Gate II - Enhanced Edition/
       characters/<Account>/campaign_progress/SoA.json
       characters/<Account>/campaign_progress/ToB.json
       characters/<Account>/campaign_progress/TBP.json
   Only a validated existing account folder is indexed. The updater waits at
   least five seconds after native BG2's last save-file write. It does not
   duplicate .CHR, .BIO, .GAM, or any other files; no game backup is made.

IMPORTANT PHYSICAL SAVE LOCATION
BG2's full multiplayer save game remains in its own normal Documents/.../mpsave
folder. The account folder's campaign_progress/*.json is a reference/index,
not a duplicate or a replacement of that full game state. BG2 resume loads the
original native save. A dynamic live mpsave junction swap between accounts was
NOT attempted: switching it with multiple connected game clients may strand
open game files or affect another account's live session.

INSTALL / TEST
1. Close BG2 and InfinityLoader game windows.
2. Extract ZIP and run All Editors/SETUP_IN_GAME_ACCOUNTS.bat using the same
   game/profile paths as V316. No preexisting accounts/CHR are deleted.
3. Launch via InfinityLoader.exe (EEex must be installed for global shortcut
   interception).
4. With player1 alive in SoA, open Options > Save Game and create an explicit
   save. Confirm it appears in the native multiplayer mpsave folder; after
   10-20s the current account's campaign_progress/SoA.json should reference it.
5. Quit to main UI, choose the same campaign and Create Game, then select
   RESUME CAMPAIGN and load the tagged save. Confirm original location and
   world/quests continue, then join the running host as another account.
6. Test all party dead during a story sequence: Escape opens Options but does
   not resurrect anyone. Test ordinary cutscene Escape remains blocked.
7. Test manual Space and clock pause from player 1 AND player 2. Verify native
   dialogue/script synchronization pauses still happen as needed.

LIMITATIONS
- Native hotkey and world state behavior must be tested in Windows/BG2/EEex;
  Python/static UI tests cannot prove engine key dispatch under every cutscene.
- This does not recover existing untagged saves automatically or relocate old
  saves into the new account's folder. Character/account permissions unchanged.
- There is no automatic save at quit, death, login, join or character export.
